Coordinated security systems and methods for an electronic device

ABSTRACT

Systems and methods for implementing security features of a mobile electronic device. The mobile electronic device comprises a first security module configured to implement a first security operation and a second security module configured to implement a second security operation. The method includes: detecting a first security event; implementing a first security operation by the first security module; triggering a second security event; and implementing a second security operation by the second security module. The first security operation includes triggering the second security event.

TECHNICAL FIELD

Embodiments described herein relate generally to the operation ofsecurity features on mobile electronic devices.

BACKGROUND

Mobile electronic devices are often equipped with a smart card such as aSubscriber Identity Module or “SIM” card in order to send and receivecommunication signals (such as a cellular phone call). Typically, suchSIM cards require network registration and activation proceduresinvolving the use of passwords. Similarly, the use of passwords or othersecurity features may be used to limit or restrict access to the SIMcard functionality.

Additionally some electronic devices also provide applicationfunctionality which is independent of the SIM card. For example, somedevices include device applications which provide address bookfunctionality, scheduling and calendar functionality, video games,digital camera picture-taking and viewing, and multi-mediapresentations, among others. Often, such applications involve thestoring and use of user data or content. Access to these applicationsand user data is typically restricted or regulated using passwords orother security features.

In the event that an unauthorized user obtains the device and enters aninvalid password to the device (often the user is provided multipleopportunities to enter a valid password), the security features deleteor otherwise restrict access to the user data and may prevent furtheruse of the device applications.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of embodiments described herein, and to showmore clearly how they may be carried into effect, reference will now bemade, by way of example, to the accompanying drawings in which:

FIG. 1 is a block diagram of a mobile device in one exampleimplementation;

FIG. 2 is a block diagram of a communication subsystem component of themobile device of FIG. 1;

FIG. 3 is a block diagram of a node of a wireless network;

FIG. 4 is a block diagram illustrating components of a host system inone example configuration; and

FIG. 5 is a flowchart illustrating steps in a method of coordinatingsecurity systems of a computing device in accordance with at least oneembodiment.

DETAILED DESCRIPTION

While certain embodiments of existing mobile electronic devices providefor the disabling of device applications upon receipt of an invalidpassword, the applicant has noted that the SIM card may remainunaffected. As a result, a thief of the device may be able to continueto utilize the communication functionality until the communicationnetwork administrators are notified and the SIM card is blocked fromaccessing the network or otherwise deactivated.

Furthermore, the applicant has also noted that in addition to SIM cards,other types of communication cards may be used in mobile electronicdevice applications. Accordingly, by way of example only, other types ofcommunication cards which might be used may include an R-UIM (removableuser identity module) or a CSIM (CDMA (code division multiple access) orCDMA 2000 subscriber identity module) or a USIM (universal subscriberidentity module) card.

Embodiments described herein are generally directed to a system andmethod that coordinates two or more typically separate security measuresor operations of a mobile communications system. In particular, theactivation of a first security measure may trigger the activation of asecond security measure.

In a broad aspect, there is provided a method for implementing securityfeatures of a mobile electronic device. The mobile electronic device maycomprise a first security module configured to implement a firstsecurity operation and a second security module configured to implementa second security operation. The method includes: detecting a firstsecurity event; initiating a first security operation by the firstsecurity module; triggering a second security event; and initiating asecond security operation by the second security module. The firstsecurity operation may include triggering the second security event.

In one embodiment of the method, detecting the first security event isperformed by a first security module. Upon detecting the first securityevent, the first security module causes the second security module toimplement the second security operation.

In some embodiments, initiating the second security module may comprisedisabling the functionality of a communication card. For example, thecommunication card may comprise a SIM card, an R-UIM card, a CSIM card,and/or a USIM card.

In some instances, detecting the first security event comprisesreceiving an authorization code and determining that the authorizationcode does not correspond to previously stored authorization data.

A computer-readable medium comprising instructions executable on aprocessor of the computing device for implementing the methods, is alsoprovided.

In another aspect, a mobile electronic device having coordinatedsecurity features is provided. The system includes: a first applicationmodule configured to provide first application functionality; a firstsecurity module coupled with the first application module, the firstsecurity module configured to regulate the provision of the firstapplication functionality by the first application module; a secondapplication module configured to provide second applicationfunctionality; and a second security module coupled with the secondapplication module and the first security module, the second securitymodule configured to regulate the provision of the second applicationmodule.

In some instances, the first security module is configured to detect afirst security event. The second security module may be configured todetect a second security event. The first security module may beconfigured to implement a first security operation upon detecting saidfirst security event, and the second security module may be configuredto implement a second security operation upon detecting said secondsecurity event.

The first security operation may comprise triggering the second securityevent to be detected by the second security module, and the secondsecurity module is configured to disable the second applicationfunctionality when implementing the second security operation.

The device may comprise a user data storage configured to store userdata and the first security module is configured to disable access tothe user data when implementing the first security operation.

In some cases, the device is provided with authorization data storageconfigured to store authorization data, and the first security module isfurther configured to receive a first authorization code and compare thefirst authorization code to first authorization data stored in theauthorization data storage. The first security module is furtherconfigured to implement a first security operation upon determining thatthe first authorization code does not correspond to the firstauthorization data.

The second security module may be further configured to receive a secondauthorization code and compare the second authorization code to secondauthorization data stored in the authorization data storage. The secondsecurity module may further be configured to implement a second securityoperation upon determining that the second authorization code does notcorrespond to the second authorization data.

In another aspect, a method for implementing security features of amobile electronic device is provided. The mobile electronic deviceincludes a communication card configured to provide a functionality; afirst security module configured to implement a first securityoperation; and a second security module configured to implement a secondsecurity operation, The method comprises: detecting a first securityevent by the first security module, wherein the first security eventcomprises receiving an invalid authorization code. The method alsoincludes implementing a first security operation by the first securitymodule, wherein the first security operation comprises triggering asecond security event. The method further includes implementing a secondsecurity operation by the second security module upon the triggering ofthe second security event, wherein the second security operationcomprises disabling the functionality of the communication card.

These and other aspects and features of various embodiments will bedescribed in greater detail below.

Some embodiments described herein make use of a mobile station. A mobilestation is a two-way communication device with advanced datacommunication capabilities having the capability to communicate withother computer systems, and is also referred to herein generally as amobile device. A mobile device may also include the capability for voicecommunications. Depending on the functionality provided by a mobiledevice, it may be referred to as a data messaging device, a two-waypager, a cellular telephone with data messaging capabilities, a wirelessInternet appliance, or a data communication device (with or withouttelephony capabilities). A mobile device communicates with other devicesthrough a network of transceiver stations.

To aid the reader in understanding the structure of a mobile device andhow it communicates with other devices, reference is made to FIGS. 1through 3.

Referring first to FIG. 1, a block diagram of a mobile device in oneexample implementation is shown generally as 100. Mobile device 100comprises a number of components, the controlling component beingmicroprocessor 102. Microprocessor 102 controls the overall operation ofmobile device 100. Communication functions, including data and voicecommunications, are performed through communication subsystem 104.Communication subsystem 104 receives messages from and sends messages toa wireless network 200. In this example implementation of mobile device100, communication subsystem 104 is configured in accordance with theGlobal System for Mobile Communication (GSM) and General Packet RadioServices (GPRS) standards. The GSM/GPRS wireless network is usedworldwide and it is expected that these standards may be supplemented oreventually superseded by newer standards such as Enhanced Data GSMEnvironment (EDGE) and Universal Mobile Telecommunications Service(UMTS), High-Speed Packet Access (HSPA) which may include High-SpeedDownlink Packet Access (HSDPA), and Ultra Mobile Broadband (UMB), etc.New standards are still being defined, but it is believed that they willhave similarities to the network behaviour described herein, and it willalso be understood by persons skilled in the art that the invention isintended to use any other suitable standards that are developed in thefuture. The wireless link connecting communication subsystem 104 withnetwork 200 represents one or more different Radio Frequency (RF)channels, operating according to defined protocols specified forGSM/GPRS communications. With newer network protocols, these channelsare capable of supporting both circuit switched voice communications andpacket switched data communications.

Although the wireless network associated with mobile device 100 is aGSM/GPRS wireless network in one example implementation of mobile device100, other wireless networks may also be associated with mobile device100 in variant implementations. Different types of wireless networksthat may be employed include, for example, data-centric wirelessnetworks, voice-centric wireless networks, and dual-mode networks thatcan support both voice and data communications over the same physicalbase stations. Combined dual-mode networks include, but are not limitedto, Code Division Multiple Access (CDMA) networks, or CDMA2000 networks,Evolution Data Only (EV-DO) networks, GSM/GPRS networks (as mentionedabove), and third-generation (3G) and beyond networks like EDGE, UMTSand HSPA, etc. Some older examples of data-centric networks include theMobitex™ Radio Network and the DataTAC™ Radio Network. Examples of oldervoice-centric data networks include Personal Communication Systems (PCS)networks like GSM and Time Division Multiple Access (TDMA) systems.

Microprocessor 102 also interacts with additional subsystems such as aRandom Access Memory (RAM) 106, flash memory 108, display 110, auxiliaryinput/output (I/O) subsystem 112, serial port 114, keyboard 116, speaker118, microphone 120, short-range communications subsystem 122 and othersubsystems 124.

Some of the subsystems of mobile device 100 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. By way of example, display 110 andkeyboard 116 may be used for both communication-related functions, suchas entering a text message for transmission over network 200, anddevice-resident functions such as a calculator or task list. Operatingsystem software used by microprocessor 102 is typically stored in apersistent store such as flash memory 108, which may alternatively be aread-only memory (ROM) or similar storage element (not shown). Thoseskilled in the art will appreciate that the operating system, specificdevice applications, or parts thereof, may be temporarily loaded into avolatile store such as RAM 106.

Microprocessor 102, in addition to its operating system functions,enables execution of software applications on mobile device 100. A setof applications that control basic device operations, including data andvoice communication applications, may be installed on mobile device 100during its manufacture. Another application that may be loaded ontomobile device 100 is a personal information manager (PIM). A PIM hasfunctionality to organize and manage data items of interest to asubscriber, such as, but not limited to, e-mail, calendar events, voicemails, appointments, and task items. A PIM application has the abilityto send and receive data items via wireless network 200. PIM data itemsmay be seamlessly integrated, synchronized, and updated via wirelessnetwork 200 with the mobile device subscriber's corresponding data itemsstored and/or associated with a host computer system. This functionalitycreates a mirrored host computer on mobile device 100 with respect tosuch items. This can be particularly advantageous where the hostcomputer system is the mobile device subscriber's office computersystem.

Additional applications may also be loaded onto mobile device 100through network 200, auxiliary I/O subsystem 112, serial port 114,short-range communications subsystem 122, or any other suitablesubsystem 124. This flexibility in application installation increasesthe functionality of mobile device 100 and may provide enhancedon-device functions, communication-related functions, or both. Forexample, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing mobile device 100.

Serial port 114 enables a subscriber to set preferences through anexternal device or software application and extends the capabilities ofmobile device 100 by providing for information or software downloads tomobile device 100 other than through a wireless communication network.The alternate download path may, for example, be used to load anencryption key onto mobile device 100 through a direct and thus reliableand trusted connection to provide secure device communication.

The subsystems 124 may include at least one suitably programmedsubsystem security module 124A configured to regulate access to one ormore of the resident applications and/or functionality 124B. As noteabove, for example, such resident applications 124B may include a PIM toprovide address book functionality, scheduling and calendarfunctionality, video games, digital camera picture-taking and viewing,and multi-media presentations, among others. Often, such applicationsinvolve the storing and use of user data or content 124C includingapplication preferences and settings. As will be understood, such usercontent 124C may be stored in whole or in part in the flash memory 108,ROM or other appropriate (typically resident) data storage, referred togenerally as 124D.

Access to these applications 124B and user data 124C may be restrictedor regulated by the security module 124A involving the use of passwordsor other security features. Such password functionality may include thestoring of authorization data 124E (which may be stored in the datastorage 124D or elsewhere). In order to utilize the applications 124Band access the user data 124C, the security module 124A may beprogrammed to require the user to enter a password or otherwise providean authorization code 124F from time to time (typically via the display110 and keyboard 116 although other mechanisms may be used), which isreceived by the security module 124A and compared to the authorizationdata 124E.

In certain embodiments, the security module 124A may be operativelycoupled to or otherwise in communication with a biometric authorizationcomponent, for example, a retinal scanner or a fingerprint scanner(although other biometric scanners might be used), configured to receiveunique biometric information from a user in order to confirm the user'sidentity. In such embodiments, the authorization data 124E mightcomprise the biometric information of one or more authorized users,while the authorization code 124F might comprise the scanned biometricinformation from a current user of the device 100.

In the event an authorization code 124F is received by the securitymodule 124A which does not match or otherwise correspond to theauthorization data 124E (illustrating one example of a “securityevent”), access to the user data 124C may be restricted (for example,the user data 124C may be encrypted or deleted), and the user may beprevented from accessing the application functionality 124B (suchprocesses may be considered “security operations”). An alternate exampleof a security event could be the sending of a specially configuredelectronic message comprising control instructions, by a networkadministrator (such as an administrator of the LAN 250 described below).Receipt of such a message may cause the triggering of a security eventand the corresponding security operation features discussed below.

Mobile device 100 may send and receive communication signals overnetwork 200 after required network registration or activation procedureshave been completed. Network access is associated with a subscriber oruser of a mobile device 100. To identify a subscriber, mobile device 100may provide for a Subscriber Identity Module or “SIM” card 126 to beinserted in a SIM interface 128 in order to communicate with a network.SIM 126 is one type of a conventional “smart card” or communication cardused to identify a subscriber of mobile device 100 and to personalizethe mobile device 100, among other things. In some alternateembodiments, the mobile device 100 may comprise an iDEN (IntegratedDigital Enhanced Network) handset, which incorporates the use of SIMcards.

In addition to SIM cards, other types of communication cards may be usedin mobile electronic device applications. By way of example only, inalternate embodiments, other types of communication cards which might beused in addition to or in place of SIM cards may include an R-UIM(removable user identity module) or a CSIM (CDMA (code division multipleaccess) subscriber identity module) or a USIM (universal subscriberidentity module) card.

Without SIM 126, mobile device 100 may not be fully operational forcommunication with network 200. By inserting SIM 126 into SIM interface128, a subscriber can access all subscribed services. Services mayinclude without limitation: web browsing and messaging such as e-mail,voice mail, Short Message Service (SMS), and Multimedia MessagingServices (MMS), and peer-to-peer messages such as PIN-to-PIN which mayalso be referred to simply as PIN messages. As used in this context, aPIN (personal identification number) generally refers to a number thatuniquely identifies the mobile device 100, and a PIN message generallyrefers to a message addressed to one or more PIN numbers. More advancedservices may include without limitation: point of sale, field serviceand sales force automation. SIM 126 includes a processor and memory forstoring information. Once SIM 126 is inserted in SIM interface 128, itis coupled to microprocessor 102. In order to identify the subscriber,SIM 126 contains some user parameters such as an International MobileSubscriber Identity (IMSI). An advantage of using SIM 126 is that asubscriber is not necessarily bound by any single physical mobiledevice. SIM 126 may store additional subscriber information for a mobiledevice as well, including datebook (or calendar) information and recentcall information.

The SIM 126 may include at least one suitably programmed SIM securitymodule 126A configured to regulate access to one or more of thecommunication functionality 124B noted previously.

Access to the SIM communication applications and functionality 126B maybe restricted or regulated by the security module 126A involving the useof passwords or other security features. Such password functionality mayinclude the storing of SIM authorization data 126C such as a PIN(personal identification number) (which may be stored in the datastorage 124D, but will often be stored in SIM data storage 126D residenton the SIM card 126). Such PIN data 126C will often be in addition tothe PUK (“personal unblocking key”) data which is uniquely assigned tothe SIM card 126, as will be understood.

In order to utilize the communication applications and functionality126B, the SIM security module 126A may be programmed to require the userto enter a password or otherwise provide an authorization code 126E fromtime to time (typically via the display 110 and keyboard 116 althoughother mechanisms may be used), which is received by the security module126A and compared to the authorization data 126C. In the event anauthorization code 126E is received by the security module 126A whichdoes not match or otherwise correspond to the authorization data 126C(also a “security event”), further access to the communicationfunctionality may be prevented. Typically, a user is given multipleattempts (e.g., three) to enter an acceptable authorization code 126E,before the communication functionality is deactivated (a “securityoperation”).

In addition, the subsystem security module 124A is operatively coupledto the SIM security module 126A, typically via the microprocessor 102.In the case of a security event being detected by the subsystem securitymodule 124A, the security module 124A is programmed to include in itssecurity operations the triggering of a security event for the SIMsecurity module 126A to detect. For example, the subsystem securitymodule 124A may be programmed to trigger the password function of theSIM security system 126A and enter one or more invalid authorizationcodes 126E until the communication functionality is disabled.

Mobile device 100 may be a battery-powered device and may include abattery interface 132 for receiving one or more rechargeable batteries130. Battery interface 132 may be coupled to a regulator (not shown),which assists battery 130 in providing power V+ to mobile device 100.Although current technology makes use of a battery, future technologiessuch as micro fuel cells may provide the power to mobile device 100. Insome embodiments, mobile device 100 may be solar-powered.

Short-range communications subsystem 122 provides for communicationbetween mobile device 100 and different systems or devices, without theuse of network 200. For example, subsystem 122 may include an infrareddevice and associated circuits and components for short-rangecommunication. Examples of short range communication would includestandards developed by the Infrared Data Association (IrDA), Bluetooth,and the 802.11 family of standards developed by IEEE.

In use, a received signal such as a text message, an e-mail message, orweb page download will be processed by communication subsystem 104 andinput to microprocessor 102. Microprocessor 102 will then process thereceived signal for output to display 110 or alternatively to auxiliaryI/O subsystem 112. A subscriber may also compose data items, such ase-mail messages, for example, using keyboard 116 in conjunction withdisplay 110 and possibly auxiliary I/O subsystem 112. Auxiliarysubsystem 112 may include devices such as: a touch screen, mouse, trackball, infrared fingerprint detector, or a roller wheel with dynamicbutton pressing capability. Keyboard 116 may comprise an alphanumerickeyboard and/or telephone-type keypad. Keyboard 116 may comprise avirtual keyboard or a physical keyboard or both. A composed item may betransmitted over network 200 through communication subsystem 104.

For voice communications, the overall operation of mobile device 100 issubstantially similar, except that the received signals may be processedand output to speaker 118, and signals for transmission may be generatedby microphone 120. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on mobiledevice 100. Although voice or audio signal output is accomplishedprimarily through speaker 118, display 110 may also be used to provideadditional information such as the identity of a calling party, durationof a voice call, or other voice call related information.

Referring now to FIG. 2, a block diagram of the communication subsystemcomponent 104 of FIG. 1 is shown. Communication subsystem 104 comprisesa receiver 150, a transmitter 152, one or more embedded or internalantenna elements 154, 156, Local Oscillators (LOs) 158, and a processingmodule such as a Digital Signal Processor (DSP) 160.

The particular design of communication subsystem 104 is dependent uponthe network 200 in which mobile device 100 is intended to operate, thusit should be understood that the design illustrated in FIG. 2 servesonly as one example. Signals received by antenna 154 through network 200are input to receiver 150, which may perform such common receiverfunctions as signal amplification, frequency down conversion, filtering,channel selection, and analog-to-digital (A/D) conversion. A/Dconversion of a received signal allows more complex communicationfunctions such as demodulation and decoding to be performed in DSP 160.In a similar manner, signals to be transmitted are processed, includingmodulation and encoding, by DSP 160. These DSP-processed signals areinput to transmitter 152 for digital-to-analog (D/A) conversion,frequency up conversion, filtering, amplification and transmission overnetwork 200 via antenna 156. DSP 160 not only processes communicationsignals, but also provides for receiver and transmitter control. Forexample, the gains applied to communication signals in receiver 150 andtransmitter 152 may be adaptively controlled through automatic gaincontrol algorithms implemented in DSP 160.

The wireless link between mobile device 100 and a network 200 maycontain one or more different channels, typically different RF channels,and associated protocols used between mobile device 100 and network 200.A RF channel is a limited resource that must be conserved, typically dueto limits in overall bandwidth and limited battery power of mobiledevice 100.

When mobile device 100 is fully operational, transmitter 152 may bekeyed or turned on only when it is sending to network 200 may otherwiseturned off to conserve resources. Similarly, receiver 150 may beperiodically turned off to conserve power until it is needed to receivesignals or information (if at all) during designated time periods.

Referring now to FIG. 3, a block diagram of a node of an exemplarywireless network is shown as 202. In practice, network 200 comprises oneor more nodes 202. Mobile device 100 communicates with a node 202 withinwireless network 200. In the example implementation of FIG. 3, node 202is configured in accordance with General Packet Radio Service (GPRS) andGlobal Systems for Mobile (GSM) technologies; however, in otherembodiments, different standards may be implemented as discussed in moredetail above. Node 202 includes a base station controller (BSC) 204 withan associated tower station 206, a Packet Control Unit (PCU) 208 addedfor GPRS support in GSM, a Mobile Switching Center (MSC) 210, a HomeLocation Register (HLR) 212, a Visitor Location Registry (VLR) 214, aServing GPRS Support Node (SGSN) 216, a Gateway GPRS Support Node (GGSN)218, and a Dynamic Host Configuration Protocol (DHCP) 220. This list ofcomponents is not meant to be an exhaustive list of the components ofevery node 202 within a GSM/GPRS network, but rather serves as a list ofcomponents that are commonly used in communications through network 200,for ease of illustration.

In a GSM network, MSC 210 is coupled to BSC 204 and to a landlinenetwork, such as a Public Switched Telephone Network (PSTN) 222 tosatisfy circuit switched requirements. The connection through PCU 208,SGSN 216 and GGSN 218 to the public or private network (Internet) 224(also referred to herein generally as a shared network infrastructure)represents the data path for GPRS capable mobile devices. In a GSMnetwork extended with GPRS capabilities, BSC 204 also contains a PacketControl Unit (PCU) 208 that connects to SGSN 216 to controlsegmentation, radio channel allocation and to satisfy packet switchedrequirements. To track mobile device location and availability for bothcircuit switched and packet switched management, HLR 212 is sharedbetween MSC 210 and SGSN 216. Access to VLR 214 is controlled by MSC210.

Station 206 comprises a fixed transceiver station. Station 206 and BSC204 together form the fixed transceiver equipment. The fixed transceiverequipment provides wireless network coverage for a particular coveragearea commonly referred to as a “cell”. The fixed transceiver equipmenttransmits communication signals to and receives communication signalsfrom mobile devices within its cell via station 206. The fixedtransceiver equipment normally performs such functions as modulation andpossibly encoding and/or encryption of signals to be transmitted to themobile device in accordance with particular, usually predetermined,communication protocols and parameters, under control of its controller.The fixed transceiver equipment similarly demodulates and possiblydecodes and decrypts, if necessary, any communication signals receivedfrom mobile device 100 within its cell. Communication protocols andparameters may vary between different nodes. For example, one node mayemploy a different modulation scheme and operate at differentfrequencies than other nodes.

For all mobile devices 100 registered with a specific network, permanentconfiguration data such as a user profile is stored in HLR 212. HLR 212also contains location information for each registered mobile device andcan be queried to determine the current location of a mobile device. MSC210 is responsible for a group of location areas and stores the data ofthe mobile devices currently in its area of responsibility in VLR 214.Further VLR 214 also contains information on mobile devices that arevisiting other networks. The information in VLR 214 includes part of thepermanent mobile device data transmitted from HLR 212 to VLR 214 forfaster access. By moving additional information from a remote HLR 212node to VLR 214, the amount of traffic between these nodes can bereduced so that voice and data services can be provided with fasterresponse times and at the same time requiring less use of computingresources.

SGSN 216 and GGSN 218 are elements added for GPRS support namely, packetswitched data support, within GSM. SGSN 216 and MSC 210 have similarresponsibilities within wireless network 200 by keeping track of thelocation of each mobile device 100. SGSN 216 also performs securityfunctions and access control for data traffic on network 200. GGSN 218provides internetworking connections with external packet switchednetworks and connects to one or more SGSN's 216 via an Internet Protocol(IP) backbone network operated within the network 200. During normaloperations, a given mobile device 100 performs a “GPRS Attach” toacquire an IP address and to access data services. This normally is notpresent in circuit switched voice channels as Integrated ServicesDigital Network (ISDN) addresses are used for routing incoming andoutgoing calls. Currently, all GPRS capable networks use private,dynamically assigned IP addresses, thus requiring a DHCP server 220connected to the GGSN 218. There are many mechanisms for dynamic IPassignment, including using a combination of a Remote AuthenticationDial-In User Service (RADIUS) server and DHCP server. Once the GPRSAttach is complete, a logical connection is established from a mobiledevice 100, through PCU 208, and SGSN 216 to an Access Point Node (APN)within GGSN 218. The APN represents a logical end of an IP tunnel thatcan either access direct Internet compatible services or private networkconnections. The APN also represents a security mechanism for network200, insofar as each mobile device 100 must be assigned to one or moreAPNs and mobile devices 100 cannot exchange data without firstperforming a GPRS Attach to an APN that it has been authorized to use.The APN may be considered to be similar to an Internet domain name suchas “myconnection.wireless.com”.

Once the GPRS Attach is complete, a tunnel is created and all traffic isexchanged within standard IP packets using any protocol that can besupported in IP packets. This includes tunneling methods such as IP overIP as in the case with some IPSecurity (IPsec) connections used withVirtual Private Networks (VPN). These tunnels are also referred to asPacket Data Protocol (PDP) Contexts and there are a limited number ofthese available in the network 200. To maximize use of the PDP Contexts,network 200 will run an idle timer for each PDP Context to determine ifthere is a lack of activity. When a mobile device 100 is not using itsPDP Context, the PDP Context can be deallocated and the IP addressreturned to the IP address pool managed by DHCP server 220.

Referring now to FIG. 4, a block diagram illustrating components of ahost system in one example configuration is shown. Host system 250 maytypically be, for example a corporate office or other local area network(LAN), but may instead be a home office computer or some other privatesystem, for example, in variant implementations. As other examples, thehost system 250 may comprise a LAN controlled by a governmental,healthcare, financial, or educational institution. In this example shownin FIG. 4, host system 250 is depicted as a LAN of an organization towhich a user of mobile device 100 belongs.

LAN 250 comprises a number of network components connected to each otherby LAN connections 260. For instance, a user's desktop computer 262 awhich may be connected to an accompanying cradle 264 for the user'smobile device 100 is situated on LAN 250. Cradle 264 for mobile device100 may be coupled to computer 262 a by a serial or a Universal SerialBus (USB) connection, for example. Other user computers 262 b are alsosituated on LAN 250, and each may or may not be equipped with anaccompanying cradle 264 for a mobile device. Cradle 264 facilitates theloading of information (e.g. PIM data, private symmetric encryption keysto facilitate secure communications between mobile device 100 and LAN250) from user computer 262 a to mobile device 100, and may beparticularly useful for bulk information updates often performed ininitializing mobile device 100 for use. The information downloaded tomobile device 100 may include certificates used in the exchange ofmessages. It will be understood by persons skilled in the art that usercomputers 262 a, 262 b will typically be also connected to otherperipheral devices not explicitly shown in FIG. 4.

Furthermore, only a subset of network components of LAN 250 are shown inFIG. 4 for ease of exposition, and it will be understood by personsskilled in the art that LAN 250 will comprise additional components notexplicitly shown in FIG. 4, for this example configuration. Moregenerally, LAN 250 may represent a smaller part of a larger network [notshown] of the organization, and may comprise different components and/orbe arranged in different topologies than that shown in the example ofFIG. 4.

In this example, mobile device 100 communicates with LAN 250 through anode 202 of wireless network 200 and a shared network infrastructure 224such as a service provider network or the public Internet. Access to LAN250 may be provided through one or more routers [not shown], andcomputing devices of LAN 250 may operate from behind a firewall or proxyserver 266.

In a variant implementation, LAN 250 comprises a wireless VPN router[not shown] to facilitate data exchange between the LAN 250 and mobiledevice 100. The concept of a wireless VPN router is new in the wirelessindustry and implies that a VPN connection can be established directlythrough a specific wireless network to mobile device 100. Thepossibility of using a wireless VPN router has only recently beenavailable and could be used when the new Internet Protocol (IP) Version6 (IPV6) arrives into IP-based wireless networks. This new protocol willprovide enough IP addresses to dedicate an IP address to every mobiledevice, making it possible to push information to a mobile device at anytime. An advantage of using a wireless VPN router is that it could be anoff-the-shelf VPN component, not requiring a separate wireless gatewayand separate wireless infrastructure to be used. A VPN connection mayinclude, for example, a Transmission Control Protocol (TCP)/IP or UserDatagram Protocol (UDP)/IP connection to deliver the messages directlyto mobile device 100 in this variant implementation.

Messages intended for a user of mobile device 100 are initially receivedby a message server 268 of LAN 250. Such messages may originate from anyof a number of sources. For instance, a message may have been sent by asender from a computer 262 b within LAN 250, from a different mobiledevice [not shown] connected to wireless network 200 or to a differentwireless network, or from a different computing device or other devicecapable of sending messages, via the shared network infrastructure 224,and possibly through an application service provider (ASP) or Internetservice provider (ISP), for example.

Message server 268 typically acts as the primary interface for theexchange of messages, particularly e-mail messages, within theorganization and over the shared network infrastructure 224. Each userin the organization that has been set up to send and receive messages istypically associated with a user account managed by message server 268.One example of a message server 268 is a Microsoft Exchange™ Server. Insome implementations, LAN 250 may comprise multiple message servers 268.Message server 268 may also be adapted to provide additional functionsbeyond message management, including the management of data associatedwith calendars and task lists, for example.

When messages are received by message server 268, they are typicallystored in a message store [not explicitly shown], from which messagescan be subsequently retrieved and delivered to users. For instance, ane-mail client application operating on a user's computer 262 a mayrequest the e-mail messages associated with that user's account storedon message server 268. These messages may then typically be retrievedfrom message server 268 and stored locally on computer 262 a.

When operating mobile device 100, the user may wish to have e-mailmessages retrieved for delivery to the handheld. An e-mail clientapplication operating on mobile device 100 may also request messagesassociated with the user's account from message server 268. The e-mailclient may be configured (either by the user or by an administrator,possibly in accordance with an organization's information technology(IT) policy) to make this request at the direction of the user, at somepre-defined time interval, or upon the occurrence of some pre-definedevent. In some implementations, mobile device 100 is assigned its owne-mail address, and messages addressed specifically to mobile device 100are automatically redirected to mobile device 100 as they are receivedby message server 268.

To facilitate the wireless communication of messages and message-relateddata between mobile device 100 and components of LAN 250, a number ofwireless communications support components 270 may be provided. In thisexample implementation, wireless communications support components 270comprise a message management server 272 and mobile data server 288, forexample. Message management server 272 is used to specifically providesupport for the management of messages, such as e-mail messages, thatare to be handled by mobile devices. Generally, while messages are stillstored on message server 268, message management server 272 can be usedto control when, if, and how messages should be sent to mobile device100. Message management server 272 also facilitates the handling ofmessages composed on mobile device 100, which are sent to message server268 for subsequent delivery.

For example, message management server 272 may: monitor the user's“mailbox” (e.g. the message store associated with the user's account onmessage server 268) for new e-mail messages; apply user-definablefilters to new messages to determine if and how the messages will berelayed to the user's mobile device 100; compress and encrypt newmessages (e.g. using an encryption technique such as Data EncryptionStandard (DES) or Triple DES) and push them to mobile device 100 via theshared network infrastructure 224 and wireless network 200; and receivemessages composed on mobile device 100 (e.g. encrypted using TripleDES), decrypt and decompress the composed messages, re-format thecomposed messages if desired so that they will appear to have originatedfrom the user's computer 262 a, and re-route the composed messages tomessage server 268 for delivery.

Certain properties or restrictions associated with messages that are tobe sent from and/or received by mobile device 100 can be defined (e.g.by an administrator in accordance with IT policy) and enforced bymessage management server 272. These may include whether mobile device100 may receive encrypted and/or signed messages, minimum encryption keysizes, whether outgoing messages must be encrypted and/or signed, andwhether copies of all secure messages sent from mobile device 100 are tobe sent to a pre-defined copy address, for example.

Message management server 272 may also be adapted to provide othercontrol functions, such as only pushing certain message information orpre-defined portions (e.g. “blocks”) of a message stored on messageserver 268 to mobile device 100. For example, when a message isinitially retrieved by mobile device 100 from message server 268,message management server 272 is adapted to push only the first part ofa message to mobile device 100, with the part being of a pre-definedsize (e.g. 2 KB). The user can then request more of the message, to bedelivered in similar-sized blocks by message management server 272 tomobile device 100, possibly up to a maximum pre-defined message size.

Accordingly, message management server 272 facilitates better controlover the type of data and the amount of data that is communicated tomobile device 100, and can help to minimize potential waste of bandwidthor other resources.

It will be understood by persons skilled in the art that messagemanagement server 272 need not be implemented on a separate physicalserver in LAN 250 or other network. For example, some or all of thefunctions associated with message management server 272 may beintegrated with message server 268, or some other server in LAN 250.Furthermore, LAN 250 may comprise multiple message management servers272, particularly in variant implementations where a large number ofmobile devices is supported.

Referring now to FIG. 5, a flowchart illustrating steps in a method ofimplementing the security features of a mobile device in accordance withat least one embodiment is shown generally as 500. Additional details ofsome of the features described below in respect of the steps of method500 may be described earlier in the present specification.

The steps of method 500 are performed at the computing device. In oneembodiment, at least some of the steps of the method are performed byone or more security modules that execute and reside on a mobile device(e.g. mobile device 100 of FIG. 1). Furthermore, the security modulesneed not be stand-alone applications, and the functionality of thesecurity modules may be implemented in one or more applicationsexecuting and residing on the mobile or other computing device.

Generally, in method 500, a security event detected by one securitymodule causes the triggering of the security features provided byanother security module. The steps of method 500 are described infurther detail below.

Method 500 commences at block 510 with the security module 124Adetermining if a security event has occurred. For example, the detectionof such a security event may result from the user attempting to accessapplication functionality 124B and has been prompted by the subsystemsecurity module 124A to input an authorization code 124F, such as apassword. The security module 124A determines if the authorization code124F corresponds to the authorization data 124E. Alternatively, aspreviously noted, a network administrator may trigger a security eventby sending an appropriately configured security message to the device100.

As noted above, in certain embodiments, the authorization code 124Fmight alternately or additionally comprise biometric data from thecurrent user. Accordingly, in such an embodiment, an invalidauthorization code as contemplated in block 510 may involve, forexample, a fingerprint swipe from the user which fails to match anauthorized fingerprint swipe stored in data storage 124D.

If no security event is detected, at block 512, the user is permitted toaccess the application functionality. For example, if the authorizationcode 124F received by the security module 124A matches or otherwisecorresponds to the authorization data 124E, the user's authorization isconfirmed. Thus, the user is permitted to access the applicationfunctionality 124B. However, if a security event is detected, at block514 the first security operation is initiated. For example, if theauthorization code 124F is invalid as it does not match or otherwisecorrespond to the authorization data 124E, the security module 124A isprogrammed to effect one or more security operations. Such securityoperations may include preventing access to the user data 124C and tothe applications 124B. As noted previously, this step may involve theencryption or deletion of the user data 124C. As well, as previouslysuggested, the user may be given multiple opportunities to enter anauthorization code 124F which corresponds to the authorization data124E.

At block 516, the first security operation also includes triggering asecond security event. At block 518, the second security event initiatesthe second security operation. For example, such a second security eventmay be triggered by the first security module 124A entering one or moreinvalid SIM authorization codes 126E until the SIM security module's126A programming initiates its security operation, such as for exampledisabling the SIM card 126 and its communication functionality.

Subsequent to the disabling of the SIM card 126 in block 516, in certainembodiments, the user may contact the communication networkadministrators to unblock the SIM card 126 to reestablish itscommunication functionality and allow the SIM card 126 to access thenetwork.

While the example embodiments discussed herein illustrate theinterconnection of a subsystem security module 124A with a SIM securitymodule 126A, it should be understood that two or more security modulesregulating access to different applications' functionality may beinterconnected in accordance with the teaching set out herein.

As will be understood, in the event a thief or an otherwise unauthorizedindividual obtains possession of the device 100, by such individualentering an invalid password to access one application functionality orotherwise triggering a security event, a domino effect will result withone or more other security modules being activated to detect acorresponding security event and implement its or their securityfeatures and restrict access to its or their corresponding applicationfunctionality.

The invention has been described with regard to a number of embodiments.However, it will be understood by persons skilled in the art that othervariants and modifications may be made without departing from the scopeof the invention as defined in the claims appended hereto.

1. A method for implementing security features of a mobile electronicdevice, the method comprising: detecting a first security event;initiating a first security operation; triggering a second securityevent; initiating a second security operation; and wherein initiating asecond security operation comprises disabling functionality of acommunication card.
 2. The method as claimed in claim 1, whereindetecting the first security event is performed by a first securitymodule.
 3. The method as claimed in claim 2, wherein the first securityoperation comprises triggering the second security event.
 4. The methodas claimed in claim 1, wherein the communication card comprises at leastone selected from the group consisting of: a SIM card; an R-UIM card; aCSIM card; and a USIM card.
 5. The method as claimed in claim 1, whereindetecting the first security event comprises receiving an authorizationcode and determining that the authorization code does not correspond topreviously stored authorization data.
 6. A mobile electronic devicecomprising: a first application module configured to provide firstapplication functionality; a first security module coupled with thefirst application module, the first security module configured toregulate the provision of the first application functionality by thefirst application module; a second application module configured toprovide second application functionality; and a second security modulecoupled with the second application module and the first securitymodule, the second security module configured to regulate the provisionof the second application module.
 7. The mobile electronic device asclaimed in claim 6, wherein the first security module is configured todetect a first security event.
 8. The mobile electronic device asclaimed in claim 7, wherein the second security module is configured todetect a second security event.
 9. The mobile electronic device asclaimed in claim 8, wherein the first security module is configured toimplement a first security operation upon detecting said first securityevent.
 10. The mobile electronic device as claimed in claim 9, whereinthe second security module is configured to implement a second securityoperation upon detecting said second security event.
 11. The mobileelectronic device as claimed in claim 10, wherein the first securityoperation comprises triggering the second security event to be detectedby the second security module.
 12. The mobile electronic device asclaimed in claim 11, wherein the second security module is furtherconfigured to disable the second application functionality whenimplementing the second security operation.
 13. The mobile electronicdevice as claimed in claim 12, wherein the device further comprises auser data storage configured to store user data and wherein the firstsecurity module is further configured to disable access to the user datawhen implementing the first security operation.
 14. The mobileelectronic device as claimed in claim 12, wherein the device furthercomprises user data storage configured to store user data and whereinfirst security module is further configured to delete the user data whenimplementing the first security operation.
 15. The mobile electronicdevice as claimed in claim 12, wherein the first security module isfurther configured to disable the first application functionality whenimplementing the first security operation.
 16. The mobile electronicdevice as claimed in claim 7, wherein the device further comprisesauthorization data storage for storing authorization data and whereinthe first security module is further configured to receive a firstauthorization code and compare the first authorization code to firstauthorization data stored in the authorization data storage.
 17. Themobile electronic device as claimed in claim 16, wherein the firstsecurity module is further configured to implement a first securityoperation upon determining that the first authorization code does notcorrespond to the first authorization data.
 18. The mobile electronicdevice as claimed in claim 17, wherein the second security module isfurther configured to receive a second authorization code and comparethe second authorization code to second authorization data stored in theauthorization data storage.
 19. The mobile electronic device as claimedin claim 18, wherein the second security module is further configured toimplement a second security operation upon determining that the secondauthorization code does not correspond to the second authorization data.20. A computer-readable medium comprising instructions executable on aprocessor of the mobile device for effecting a method for implementingsecurity features of a mobile electronic device, the method comprising:detecting a first security event; initiating a first security operation;triggering a second security event; and initiating a second securityoperation.
 21. A system for implementing security features of a mobileelectronic device, the system comprising a processor on which anapplication executes, wherein the application is programmed to perform amethod for implementing security features of a mobile electronic device,the method comprising: detecting a first security event; initiating afirst security operation; triggering a second security event; andinitiating a second security operation.
 22. A method for implementingsecurity features of a mobile electronic device, wherein the mobileelectronic device comprises: a communication card configured to providea functionality; a first security module configured to implement a firstsecurity operation; and a second security module configured to implementa second security operation, wherein the method comprises: detecting afirst security event by the first security module; wherein the firstsecurity event comprises receiving an invalid authorization code;implementing a first security operation by the first security module;wherein the first security operation comprises triggering a secondsecurity event; implementing a second security operation by the secondsecurity module upon the triggering of the second security event; andwherein the second security operation comprises disabling thefunctionality of the communication card.